perm filename GOBUG.MSG[GO,ALS] blob
sn#105694 filedate 1974-06-12 generic text, type T, neo UTF8
00100 R GO
00200 O
00300 BEGIN (COPIED INTO [1,GJA])
00400 B
00500 J11
00600 CAUSES ILLEGAL UUO AT USER 22401
00700
00800 IT IS PROBABLY COINCIDENTAL THAT GO`S CRASH IS ASSOCIATED
00900 WITH THE FOLLOWING BUG SINCE IT HAS NOT CRASHED IN SIMILAR
01000 CASES WHERE THE BUG WAS APPARENT:
01100
01200 THE BUG IS THAT IT DOES NOT REALISE THAT A GROUP CAN SOMETIMES
01300 BE SAVED BY CAPTURING SOME OF THE ATTACKING STONES, E.G.,
01400 NOTE IT PLAYED J10 EXPECTING, PERHAPS, TO CAPTURE H10, NOT
01450 NOTICING THAT J11 REPELLS THE ATTACK BY CAPTURING SOME OF THE
01500 ATTACKING STONES. THE MORE COMMON AND OBVIOUS CASE IS WHERE
01600 IT FAILS TO CAPTURE MY ATTACKING PIECES IF IT CAN ESCAPE BY
01650 CONNECTING.
01700
01800 A USEFUL FEATURE WOULD BE FOR GO TO DISPLAY THE NUMBER OF
01900 STONES CAPTURED BY EACH SIDE, AND TO GENERATE A SCORE
02000 AT THE END.
02100
02200 -- JAN KOK